Skip to content

Conversation

@alecslupu
Copy link
Member

I was not very sure if we should have this automatically, so i have created as a stand alone PR. It requires #155 before merging.

@andreslucena andreslucena requested a review from fblupi December 11, 2025 08:58
Copy link
Member

@fblupi fblupi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is needed. The capistrano/rails/migrations already runs the pending migrations.

AFAIK, this line is using this gem: https://github.com/ilyakatz/data-migrate. And it will run the migrations inside the db/data directory which doesn't exist in our case.

@alecslupu
Copy link
Member Author

AFAIK, this line is using this gem: ilyakatz/data-migrate. And it will run the migrations inside the db/data directory which doesn't exist in our case.

Yes, you are right. On MetaDecidim the folders do not exist. however, we deployed data-migrate in 0.31, and instructed to look into Decidim's source code for migration files ...

@fblupi fblupi self-requested a review January 20, 2026 15:40
@fblupi fblupi merged commit 27abc31 into master Jan 20, 2026
1 check passed
@fblupi fblupi deleted the chore/add-capistrano-data-migrate branch January 20, 2026 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants